-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
korean families r01: added #1459
Conversation
Ok, I've added all the other families apart from:
Gaeugu and Sunf don't have a Regular weight. They do have Mediums weights. @davelab6 shall I rename the Medium weights to Regular? I think we should rename the fonts which have "Korea" in the name. Still keep this open. I need to do further tests. I've updated the Nanum fonts so I'd like to show theirs been an improvement. |
Yes :) cc @aaronbell |
I don't think there'd be issues with switching Medium to Regular (where no Regular exists). |
ofl/nanumbrushscript/METADATA.pb
Outdated
@@ -1,16 +1,16 @@ | |||
name: "Nanum Brush Script" | |||
name: "Nanum Brush" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't do that! :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that it would be good to maintain consistency between "Nanum Brush Script" and "Nanum Pen".
So either "Nanum Brush Script" and "Nanum Pen Script" or "Nanum Brush" and "Nanum Pen".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Today on https://fonts.google.com/?subset=korean they both have "script" appended
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh! Well never mind me then :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to hold off merging this until the family names are confirmed :) |
The Font Book error message is caused when font nametable records are empty. e.g
Many of the fonts in this pr have blank copyright strings. @davelab6 shall I remove the record or should I insert a placeholder like "Copyright the {{ Family }} Project Authors". Either way, it will solve this issue |
Project authors please |
@davelab6 I'm done but have a few questions. in ofl/hanna I added the suffix .korean to the existing font which is served on early access Is this correct? I also think I should squash these commits and write a good pr message outlining what we've done. |
Cute Font also fails ots so I have removed it. Round tripping ttx did not solve it. Shall i readd it anyway? |
The fonts already on Early Access should be dealt with in another PR. Nothing that fails OTS should be added. |
Ok, here's my plan.
|
No abbreviations
Korean Font binaries have been mastered by Aaron Bell, https://www.sajatypeworks.com
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
@m4rc1e is this ready to merge? |
Yes |
@davelab6 All families are now added. CuteFont works just fine with the removed GPOS table. |
|
I've started collecting my adhoc font engineering scripts The scripts for this project can be found here |
Should be in https://github.com/googlefonts/tools
|
Korean Font binaries have been mastered by Aaron Bell, https://www.sajatypeworks.com
Browser diff images
https://drive.google.com/file/d/1qKvlXHytLheXr2fmaVoCWAm5Grwi0gvR/view?usp=sharing
FB reports
logs.zip
These fonts don't clear FB well. A lot of the errors are related to our test suite. Tomorrow, I will highlight these and file relevant errors to FB.
I've ran every font through diffbrowsers and they all work on Win7 IE9 to OSX Safari. Some of the diffs in IE9 contain black areas. This is caused by Browserstack, not the fonts.
I still have further fonts to pr so keep this open. I'll revise the commit message and this pr text.